home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
BBS Toolkit
/
BBS Toolkit.iso
/
remote
/
james213.zip
/
JAMES.DOC
< prev
next >
Wrap
Text File
|
1992-08-15
|
67KB
|
1,856 lines
- JAMES 2.13 -
"The Message & File manager"
Version 2.13 - release
(c) 1990-1992
J.Berends
All Rights Reserved
TABLE OF CONTENTS
──────────────────────────────────────────────────────────────
PREAMBLE AND CREDITS . . . . . . . . . . . . . . . . . . 2
OVERVIEW AND FEATURES . . . . . . . . . . . . . . . . . . 3
LICENSING INFORMATION . . . . . . . . . . . . . . . . . . 4
HOW TO REGISTER . . . . . . . . . . . . . . . . . . . . . 6
REGISTRATION FORM . . . . . . . . . . . . . . . . . 7
INSTALLATION . . . . . . . . . . . . . . . . . . . . . . 9
CONFIGURATION . . . . . . . . . . . . . . . . . . . . . . 10
JAMESCFG . . . . . . . . . . . . . . . . . . . . . . 10
Dos . . . . . . . . . . . . . . . . . . . . . . 10
Shell to Dos . . . . . . . . . . . . . . . 10
Exit . . . . . . . . . . . . . . . . . . . 10
Main . . . . . . . . . . . . . . . . . . . . . 11
Addresses . . . . . . . . . . . . . . . . 11
Names . . . . . . . . . . . . . . . . . . 11
Manager Names . . . . . . . . . . . . . . 11
Switches . . . . . . . . . . . . . . . . . 12
Local . . . . . . . . . . . . . . . . . . . . . 14
BBS File Areas . . . . . . . . . . . . . . 14
Skipfiles . . . . . . . . . . . . . . . . 14
LogFiles . . . . . . . . . . . . . . . . . 14
Local Boards . . . . . . . . . . . . . . . 14
CC Addressee . . . . . . . . . . . . . . . 14
Network . . . . . . . . . . . . . . . . . . . . 15
Nodes . . . . . . . . . . . . . . . . . . 15
Magic Names . . . . . . . . . . . . . . . 15
File Areas . . . . . . . . . . . . . . . . 17
Miscellaneous . . . . . . . . . . . . . . . . . 19
Origin Lines . . . . . . . . . . . . . . . 19
Days . . . . . . . . . . . . . . . . . . . 19
Months . . . . . . . . . . . . . . . . . . 19
Export . . . . . . . . . . . . . . . . . . . . 20
Configuration . . . . . . . . . . . . . . 20
File Areas . . . . . . . . . . . . . . . . 20
Local Boards . . . . . . . . . . . . . . . 20
Nodes . . . . . . . . . . . . . . . . . . 20
Magic Files . . . . . . . . . . . . . . . 20
Tick Areas . . . . . . . . . . . . . . . . 20
JAMES COMMANDLINE PARAMETERS . . . . . . . . . . . . . . 21
? . . . . . . . . . . . . . . . . . . . . . . . . . 21
C= . . . . . . . . . . . . . . . . . . . . . . . . . 21
T= . . . . . . . . . . . . . . . . . . . . . . . . . 21
M= . . . . . . . . . . . . . . . . . . . . . . . . . 22
B= . . . . . . . . . . . . . . . . . . . . . . . . . 22
I . . . . . . . . . . . . . . . . . . . . . . . . . 22
X . . . . . . . . . . . . . . . . . . . . . . . . . 22
N . . . . . . . . . . . . . . . . . . . . . . . . . 22
E . . . . . . . . . . . . . . . . . . . . . . . . . 23
R . . . . . . . . . . . . . . . . . . . . . . . . . 23
U . . . . . . . . . . . . . . . . . . . . . . . . . 23
W . . . . . . . . . . . . . . . . . . . . . . . . . 23
MGR . . . . . . . . . . . . . . . . . . . . . . . . 23
TIC . . . . . . . . . . . . . . . . . . . . . . . . 24
SCAN . . . . . . . . . . . . . . . . . . . . . . . . 24
LIST . . . . . . . . . . . . . . . . . . . . . . . . 25
H . . . . . . . . . . . . . . . . . . . . . . . . . 25
FL= . . . . . . . . . . . . . . . . . . . . . . . . 25
ON= . . . . . . . . . . . . . . . . . . . . . . . . 25
0=..9= . . . . . . . . . . . . . . . . . . . . . . . 25
CC . . . . . . . . . . . . . . . . . . . . . . . . . 26
SR . . . . . . . . . . . . . . . . . . . . . . . . . 26
SM . . . . . . . . . . . . . . . . . . . . . . . . . 26
LOCAL . . . . . . . . . . . . . . . . . . . . . . . 26
JAMES MESSAGE METASTRINGS . . . . . . . . . . . . . . . . 27
Names . . . . . . . . . . . . . . . . . . . . . . . 27
Addresses . . . . . . . . . . . . . . . . . . . . . 28
Files . . . . . . . . . . . . . . . . . . . . . . . 29
Sizes . . . . . . . . . . . . . . . . . . . . . . . 30
Statistics . . . . . . . . . . . . . . . . . . . . . 31
FILE NAMING CONVENTION . . . . . . . . . . . . . . . . . 33
EXAMPLE MESSAGE FILES . . . . . . . . . . . . . . . . . . 34
This document makes reference to a number of third-party
products. All copyrights, trademarks and reserved rights held
in these products are acknowledged.
1
PREAMBLE AND CREDITS
──────────────────────────────────────────────────────────────
I started writing James early 1990 because my HD became more
and more filled with programs which all did something with the
message base of my RemoteAccess BBS. Those programs filled
about 800Kb of my diskspace, and I needed the space. I decided
it was time to write my own message butler. After about two
months of development I released the first version of James.
Now, almost two years later, James can do almost anything with
messages, and files received through your mailer.
I'd like to thank the following persons for their contributi-
ons (in no particular order) - all of them have played a part
in the development of James:
Jos Bergman, Jos Chrispijn, Christophe David, Glenn Harwood,
Sandra Nooren, Anton Hovestad, Rob Meulendijks, Hans de Vor,
Peter Sykora, Daniel Docekal, Johan Klaassen, Barry Geller.
Jan Berends,
Groningen.
2
OVERVIEW AND FEATURES
──────────────────────────────────────────────────────────────
James The Message & File manager (henceforth known as James)
is a message butler and file manager for Bulletin Boards with
a hudson message base an a FidoNet compatible mailer with a
*.MSG netmail message base. It has many features in it, so you
no longer have the need for that other dozen message and file
managing programs. James requires little memory.
With James you can create a lot of different messages:
- create netmail
- create echomail
- create local mail
- generate file requests
You can also do the following things:
- import netmail into a hudson messagebase
- export netmail from a hudson messagebase
- send message containing information about new files
- export message to predefined persons from your local boards
- search though download areas for files and create a message
With files you can do this:
- process inbound files
- send inbound files to downlinks
- process tick files
- send tick files to your downlinks
- remove old files from your file areas
James can perform a lot more tasks. This is only a selection
of features available in James.
3
LICENSING INFORMATION
──────────────────────────────────────────────────────────────
"James" refers to the executable programs and documentation
contained in the James distribution archives released by Jan
Berends.
This program is not freeware. This is SHAREWARE which means it
is user-supported software. If you use this program for more
than 30 days, you are asked to register. 50 Guilders is not a
lot to ask. As a bonus, registered users will get some extra
options.
The concept works only with your support. If you find that you
can use this program, then a registration fee of 50 Guilders
will help defray the development cost and encourage the aut-
horship of other programs that might be useful to you. A
registration form for this purpose is included with the James
distribution archive and is called JAMESREG.DOC.
James is Copyrighted 1990-1992 by Jan Berends, ALL RIGHTS
RESERVED WORLDWIDE. You may copy the program and documentation
for backup purposes. You also may copy and share UNMODIFIED
copies of the program package, providing that the copyright
notice is reproduced and included on all copies. You may not
sell the product for a fee and/or distribute the product along
with other products without expressed written permission from
the author of James, nor may you modify or remove the copy-
right notice from the program or the documentation.
Jan Berends shall not be held responsible for any damage
incurred by the user to hardware, software or peripheral
devices during the operation of James.
This program has been successfully tested on a PC/XT clone,
286, 386SX, 386DX and 486 machines.
Comments, suggestions and bug reports are welcome. If you have
any, you can call one of the James Support Systems listed
below, and leave a message to the Sysop. If you are reporting
a bug, please give as much detail as possible about the pro-
blem you have. When possible, send a copy of the configuration
files also.
4
James Support Systems
BBS Name Phone Net Address
HIO-BBS (+31)50-712756 2:282/5 V32/V42B
RAccess JayBee (+31)38-541358 2:512/146 HST/V32B/V42B
AllTime Board (+31)1185-2213 2:285/402 HST/V32/V42B
Googol (+31)4927-65271 2:284/105 V32B/V42B
5
HOW TO REGISTER
──────────────────────────────────────────────────────────────
Print or reproduce the registration form in the JAMESREG.DOC
file and send it with your registration payment to:
"Registration/JAMES"
J.Berends
Koolstraat 21a
9717 KB GRONINGEN
HOLLAND
PostGiro: 5579328
* You MUST fill out the registration form correctly in order
for your details to be processed. Not doing so will result
in delays in your key delivery.
* Cheques and money orders should be made payable to the
person at your registration site.
6
REGISTRATION FORM
──────────────────────────────────────────────────────────────
Enclosed is my registration fee for JAMES:
Name:
Street:
City: State: Zip:
BBS Name as it appears in JAMES.CFG:
Sysop Name as it appears in JAMES.CFG:
BBS Phone: Net/Node Number:
Opening hours of BBS:
Type of computer
What do you like about James?
Program Suggestions/Comments
7
THE KEY SYSTEM
──────────────────────────────────────────────────────────────
Upon registering you will receive your uniquely generated key.
Each key is a small file approximately 1/2K in size which
contains information about your registration. To install the
key, simply rename it to JAMES.KEY and copy it to your James
system directory.
When James detects a valid key it switches into registered
mode.
Features marked with a {+} are only available when James is
running in registered mode.
It should be made absolutely clear that James is still fully
functional before it is registered; the bonus features are
'nice' but their absence makes it no less usable. James is not
and never will be 'DemoWare' or 'ExpireWare'.
WARNING! Your key is unique, and under NO circumstances should
it be made available to anyone else. Doing so is a direct
violation of the agreement entered into with us by registe-
ring.
8
INSTALLATION
──────────────────────────────────────────────────────────────
James should run on any IBM 80x86 compatible computer. The
only other program you will need in addition to the release
package is DOS version 3.30 or higher.
The minimum memory requirement is 200K but 512K is recommen-
ded.
1. Ensure that your CONFIG.SYS file contains these statements:
FILES=20
BUFFERS=25
If you are running in a multi-tasking system, you may need
to increase the number of file handles that DOS can open at
one time, by raising the 'FILES' value. You should also
have loaded 'SHARE'. This utility allows you to open one
file by two programs at the same time. If you haven't
loaded SHARE, but are running in multi-tasking mode, you
are asking for disaster.
2. Create a directory to put the main program files in. The
configuration example that follows later assumes that this
directory (the SYSTEM directory) is C:\JAMES.
3. Ensure that your AUTOEXEC.BAT file contains a command to
set the environment variable James to your SYSTEM directo-
ry, so James can find its configuration and message files:
SET JAMES=C:\JAMES
4. Copy all of the executable files from the James distributi-
on package into the SYSTEM directory.
5. If you have the program Pretty Good Privacy, written by
Philip Zimmermann, you can assure that the files came from
the Author of James by running:
"PGP James.Ctx James.Exe" When it succeeds, you have a good
copy of James. The .Ctx files are also in the distribution
package.
6. Read the manual (you are well on your way yet!).
This completes the installation, and you are now ready to move
to the CONFIGURATION section.
9
CONFIGURATION
──────────────────────────────────────────────────────────────
JAMESCFG
Return to the James system directory again, and fire up the
configuration utility, JAMESCFG.EXE. You will use this to
select the configuration options and maintain your particular
system. You will see that there are six main configuration
menus. When you have a monochrome monitor, you can enter a /M
on the commandline, in order to use only black and white. When
you want to enter an other configuration than the default
James.Cfg, enter it also on the commandline after JamesCfg.
All addresses in JamesCfg should be entered completely!
JAMESCFG - Dos
──────────────────────────────────────────────────────────────
Shell to Dos - Use this option for a temporary shell to Dos.
You can also press ALT-Z from anywhere in JamesCfg to shell to
Dos.
Exit - Select this item when you want to leave JamesCfg.
Escape from the main menu has the same effect.
10
JAMESCFG - Main
──────────────────────────────────────────────────────────────
Addresses - Use this window to enter you network address (if
any). If you have any alias addresses (AKA's) you may enter
these in one or more of the nine slots provided. Behind each
address you can enter the netmail board for that address uses
in your Hudson message base. When you want to use the Import
netmail function, you have to define a netmail board for every
one of your addresses. When sending messages James will try to
find the address 'closest' to that of the addressee when no
address is specified.
Names - In this section you tell James where all files have to
be stored or can be found. Also some other system dependent
names have to be entered in this window:
Sysop Name : Name of sysop of BBS.
Board Name : Name of BBS.
Messagebase Path: Hudson messagebase.
Netmail Path : *.MSG netmail directory.
Mailer Path : Mailer semaphore directory.
Inbound Path : Inbound files directory.
Outbound Path : Outbound directory for MGR and TIC
functions. This directory should only
be used by James.
Swap Path : Where to place swap files.
Queue Path : Where D'Bridge stores its queue files
Helpfile Name : Name of file containing help message
for manager reply.
Log File : Filename of the system log.
Log Level : What should be written to logfile
- 0 = No logging
- 1 = Standard logging
- 2 = Full logging.
Mailer : Which mailer do you have
- FrontDoor
- D'Bridge
- None.
Manager Names - In this section you can enter 7 names where
the James -Scan function should respond to. The first three
names can not be changed.
11
Switches - This section deals with many of the global settings
in relation to messages.
Touch Cfg File Use the date and time of the Configuration
file to keep track of the date and time the
last new files scan has been done. This de-
faults to No. The JAMES.EXE file will be used
for this purpose.
Force Rescan Create messagebase rescan semaphore files for
mailer whenever a echomail/netmail message
has been sent.
Show Size Show size of listed file after filename in
messages where newfiles or files found after
a searchrequest are being displayed.
Show descripti- Show description of listed file in messages
on where newfiles or files found after a search-
request area being displayed.
Add Private Show files which have NO description in FI-
Files LES.BBS in newfiles or searchrequest reply
messages.
Show Area Name Show name of file area if newfiles or search-
request messages.
Insert Blank Insert a cosmetically good looking blank line
Line between to file areas in newfiles messages.
Tabulate De- Split description of files over more than one
scriptions line when they get too long.
Send Empty New Send new files message even when no new files
Files were found.
Send Empty Send searchrequest reply message even when no
Search Requests requested files area being found. Only recom-
mended when replies are being sent by net-
mail.
Suppress Scree- Do not write anything to screen after reading
nOutput the configuration file.
12
Compress Mail D'Bridge has the capability to 'compress'
netmail messages, in order to keep the net-
mail directory clean. This option will only
work when you have also selected D'Bridge as
a mailer in the Names section. Set this opti-
on to Yes, when you want to use it.
Clear Statis- James keeps track of how many messages have
tics On been sent. You can define on what day the
statistics have to be set to 0.
Maximum # Wild- Maximum number of "?" in a searchrequest fi-
cards lename. '*' will be expanded to '?'. A recom-
mended value here is 5.
Minimum # Cha- Minimum number of characters in a searchre-
racters quest when searching by description (when no
wildcards area in searchstring).
Days to keep Number of days to keep a file CRC in the JA-
dupes MES.DUP file. These CRC's are calculated over
all files processed by the /MGR, /TIC and /H
function.
13
JAMESCFG - Local
──────────────────────────────────────────────────────────────
BBS File Areas - In this section you can enter the information
about you File Areas.
Path Directory where the files in this area are
being stored
Description Description of this area (Used in newfile
messages).
SearchRequests Weather this file area is to be searched when
a searchrequest is being processed.
NewFiles Weather this file area has to be searched for
new files.
Group Group to which this file area belongs for
announcement messages.
Skipfiles - Here you define which files should never be repor-
ted in newfiles messages. This is useful for files like ALL-
FILES.ZIP which probably will be new every day. It thus is
nonsense to announce this file every day.
LogFiles - Here you tell James which logfiles should be se-
arched when James is checking for New Users or for Uploaders.
Local Boards - Here you define The boardnumber and a descrip-
tion of the message boards in your Hudson messagebase which
have to be searched for messages addressed to people listed in
the datafile specified with the /FL function.
CC Addressee - In this window you specify the information
about the addressee of Carbon Copy messages which will be send
when you specify the /CC parameter on the commandline:
Name : Name of Carbon Copy addressee.
Address : Optional netmail address of CC addressee.
Board : Hudson messagebase Boardnumber.
You have to specify OR Address OR Board.
Subject : Subject which will be given to CC message.
Attributes: Attributes which will be given to CC message.
14
JamesCfg - Network
──────────────────────────────────────────────────────────────
Nodes - In this section you can define your uplinks and down-
links. Use Insert to add a new node-definition, Delete to
remove a node-definition, and Enter to edit an existing node-
definition.
Address Net address of node.
Sysop name Name of sysop (will be used for all messages
send to node).
Groups Controls which areas and magic files a node
can connect to/disconnect from.
Password Defines the password for the JamesMgr and
Tick functions.
Use Aka Use which Aka when sending messages to this
node. This will default to the closest ad-
dress defined in the Addresses section.
Pointinfo Include pointinfo in ticfiles.
Status Defines the status of all messages send to
this node.
Magic Names - In this section you define the magic files.
Magic files are filemasks of files which you receive through
your mailer in your inbound directory and want to process
automatically. When you have downlinks, you can define them
also. Whenever you receive a file defined as a magic file, it
will be send on to your downlinks.
MagicName Name of magic used for connecting/disconnec-
ting files.
FileMask File mask of file. Wildcards are supported.
15
Description Description of file used for manager messag-
es. This description will be inserted in the
Files.BBS file. You can use some meta-strings
in the description:
- %1-%8 for the first 'till the eighth cha-
racter of the filename.
- %9-%11 for the first 'till the third cha-
racter of the extension.
Destination Where to move the file to.
Group Defines a group to which this file belongs.
downlinks requesting a magic-file though a
manager request must have the same group in
their groups listing in order to be able to
connect/disconnect the file.
On Days You have to define on which day the file will
be processed.
Keep Latest Keep latest allows you to control the number
of files hold in the destination directory.
It is unnecessary to keep all received node-
diff's for example. When you set this number
to 3 for example, the latest 3 nodediff's
will remain in this directory. Set this num-
ber to 0 if you want to keep all files.
Commands The commands entered here will be executed
when the file has been found in the inbound
directory prior to moving the file to its
destination directory. Commands should be
separated by ';'. When the line is too short
for all your commands, simply create a batch-
file containing all your commands, and enter
the name (and path) of your batchfile.
You can use three macro on this line:
%1 for complete filename+path
%2 for filename
%3 for extension
16
Nodes Here you define the nodes you want to send
the file to whenever it has been found in
your inbound directory. James will create a
file-attach message for each node.
File Areas - In this section you define your Tick areas. Tick
areas are file-areas somewhat like you have echomail areas.
Each Ticked file you receive will be accompanied by a little
control file containing all the information about the file
such as name, size, description, from who you receive the
file, who have received this file etc. The advantage is, that
you do not have to know the name of the file. You only define
an area, and all files receive in that area will be processed.
An other advantage of a definition in a Tick-area instead of
as a magic file is that the description of the file will come
with the file. So the description in your Files.BBS will be
the description coming with the file, not the description
defined in your setup. The password used for the control files
is the password defined in the Nodes section.
Something about security: each file received in a tick area
will be checked for the following things:
- does the area exist?
- do you allow to receive files from the sender?
- is the password correct?
- is the CRC32 of the file the same as in the control file?
- is it NOT a duplicate file?
when the file passes all those tests it will be processed.
Whenever one of these tests fails, the controlfile will be
renamed to *.BAD, and James will skip to the next file.
AreaTag This is the name of the area. This name will
be in the tick control files coming with the
files.
Description Description is the description shown in mana-
ger request messages.
Destination Destination is the directory where the files
received in this area will be moved to. If
this you leave this empty, the file will be
moved to the outbound directory.
17
Group Defines a group to which this file belongs.
downlinks requesting a magic-file though a
manager request must have the same group in
their groups listing in order to be able to
connect/disconnect the file.
Use Replace Use replaces defines whether or not the re-
place option should be used for this area.
The replace option is activated whenever the
tick control file accompanying the file con-
tains the REPLACES keyword. When James finds
the file following this keyword, James will
delete this file when you activate this opti-
on. The filename may NOT contain any wild-
cards. This is done for security reasons, in
order to disallow things like REPLACES *.*. I
suggest you only activate this section for
areas where it is useful to use this option.
Save Info This option defines whether the information
of a file should be saved in order to make it
possible to announce the newly received files
in this area in an (echo)mail message. James
will store the information in a file called
JAMES.TCI in your James directory.
Nodes Nodes defines you UPLINK and downlink nodes.
Pressing enter on a defined nodenumber allows
you to define whether a node is allowed to
send files TO you in this particular area
and/or is allowed to receive files FROM you.
When you do not specify your uplink here with
receive status, tick's received in this area
will NOT be processed.
In order to know whether a file has been processed before or
not, does James keep a duplicate file. This file contains a
CRC32 check over the received file. This duplicate checking is
done for both the Magic files and the files received in a tick
area. The Areatag or Magicname will also be included in the
duplicate check in order to allow a file to pass your system
in more than one area.
18
JamesCfg - Miscellaneous
──────────────────────────────────────────────────────────────
Here you can define some global texture to give your messages
an extra good 'looking'.
Origin Lines - With origin lines you define the origin lines
james will add to your echomail messages. The first origin
line is the default origin.
Days - This section allows you to define the full names of the
days in your own language. This gives the messages you send an
extra good look, as most other programs insert the default
English name of the days.
Months - This section allows you to define the full names of
the months in your own language.
19
JamesCfg - Export
──────────────────────────────────────────────────────────────
In the export section you can export you configuration to a
readable textfile. This is very useful when you have a bug-
report or area trying to find out where a problem is in your
setup.
Configuration - Most global option will be exported here, such
as pathnames, days, months and origin lines.
File Areas - This exports your local file areas.
Local Boards - Here will your local boards be exported as you
have defined them for use with the Forward Local function.
Nodes - This section will export the information defined about
your uplinks and downlinks.
Magic Files - Magic files defined in the Network/magic Files
section will be exported here.
Tick Areas - This will export all the information defined
about you Tick file areas.
All of above - This will export the total configuration of
James.
20
JAMES COMMANDLINE PARAMETERS
──────────────────────────────────────────────────────────────
James has many commandline parameters. Each one has its own
special function. Some parameters can be used together with
others, other parameters must be used as the only parameter.
Some other parameters can only be used with others. All this
will be explained in the following section.
Commandline parameters should be preceded with an '-' or '/'.
All file specified on the commandline (and all other files)
will first be looked for in the current directory, and when
not found there, James will look in the directory specified
with the James environment parameter. All addresses should be
entered completely!
When an example contains parameters which you do not under-
stand at the time you read them, don't bother. When you have
read this complete manual, you will understand them.
? - This parameter will display the help message.
Example: James -?
C= - With this parameter you can define an alternate configu-
ration file. The default extension for the configuration file
is .CFG. This parameter can be used with any other commandline
parameter.
Example: James -C=MyCfg -I
T= - This parameter defines the addressee of your message, or
a file containing addressees. This parameter should be used
with at least the M parameter, and the B or N parameter.The
format of this parameter is:
-T=<">Addressee<,NetAddress><;Attributes><">|@AddresseeFile
- Addressee is the name of the addressee, underscores
will be translated to spaces.
- NetAddress is the netmail address of the addressee
- Attributes area the attributes given to the message
Valid attributes are:
C Send netmail with Crash priority
D Send netmail Direct to addressee
E Delete attached file when send
F File attached (first line of message is filename)
H Hold message
I Send netmail with Immediate priority
K Kill netmail message when send
21
P Message is Private
R Request a file (first line of message is filename)
T Truncate attached file when send
U Update request (first line of message is filename)
- AddresseeFile is an ascii file containing one addressee
per line.
Examples: James -T=Jan_Berends -M=MyMsg -B=14
James -T="Jan Berends,2:282/500.1" -M=Test -N
James -T=@Nodes.Dat -M=TestMsg -N
James -T=Jan_Berends,2:282/500.1;PK -M=Test -N
M= - The M= parameter defines which ascii file should be used
as the message body.
Example: James -M=Message.Txt -R -B=34
B= - The B= parameter defines the boardnumber in your Hudson
messagebase. This parameter can be used with the R and the M
parameter.
Example: James -B=13 -M=NewMsg.Txt -T=Sysop -E=1,2
{+} I - The I parameter invokes the Import Netmail function. James
scans your netmail directory for netmail message addressed to
one of your addresses, and when found imports that message
into the defined Hudson message board. This parameter should
be the only on the commandline.
Example: James -I
{+} X - The X parameter invokes the Export Netmail function. James
scans you entire Hudson messagebase for messages with netmail
status, which are not yet exported. When found, James will
create a new message in your netmail directory, and deleting
or marking as received the message in your Hudson messagebase.
This parameter should be the only on your commandline.
Example: James -X
N - The message send will be a netmail message. This parameter
can be used with the R and the T= parameter. The format of
this parameter is:
-N<=AddressNumber>
- AddressNumber can be a number from 1 till 10.
Example: James -N -R
James -N=2 -M=ThisMsg -T=Jan_Berends,2:282/5;PK
22
E - The message send will be an echomail message. James will
append an origin line and a tearline to your message. The
format of this parameter is:
-E<=OriginNumber<,AddressNumber>>
- OriginNumer is the number of the origin line to use
- AddressNumber is the number of the address to use
This parameter can be used with the R end T= parameter.
Example: James -E -B=2 -T="Jan Berends" -M=Msg
James -E=2 -B=7 -R
R - When you use this parameter James will scan your Hudson
messagebase for messages addressed to James and/or AllFix. You
have to specify a boardnumber (B=) in which James will search
on the commandline. You can also use the M= parameter to
define the message send to the person who requested a search.
All reply's will default be sent in NETMAIL. Locally generated
message will NOT be answered.
Example: James -R -B=17
James -R -B=23 -M=Answer
James -R -B=41 -E=1,4
{+} U - This parameter tells James to check the logfile(s) defined
in the Local/LogFiles section of JamesCfg for uploaders. James
will place the defined message in the Hudson message board you
define. You can add the status bits given to the message with
an =<status bits> after the U parameter.
Example: James -U -B=17 -M=UplFiles
James -U=P -B=17 -M=UplFiles
{+} W - This parameter tells James to check the logfile(s) defined
in the Local/LogFIles section of JamesCfg for new-users. James
will place the defined message in the Hudson message board you
define. You can add the status bits given to the message with
an =<status bits> after the W parameter
Example: James -W -B=17 -M=NewUsers
James -W=P -B=17 -M=NewUsers
MGR - The Mgr parameter is a parameter which invokes a lot of
actions when given on the commandline. First of all it will
23
check your inbound directory for files which match one of the
filemask defined for your magic files. When james finds one of
those files, it will check if it is not a duplicate file. Than
James will write all defined commands to a files called Ja-
mes$$$.Bat, and will execute this file. When all this has
succeeded, James will move the file to it's destination direc-
tory, and create a file-attach netmail message for all the
connected nodes. You can define a message which has to be send
with the file. If you do not define a message, James will send
an empty message.
When James has checked all magic files, and performed all his
tasks, James will clean up the files you have defined. When
you have defined a non-zero number at the Keep-latest prompt
James will remove files matching the Filemask from the desti-
nation directory, in order to keep the latest number of those
files you have defined. When you have defined a 0, James will
remove NO files. When James removes files, James will also try
to remove the description from your Files.BBS. The Mgr Functi-
on can be executed on the same commandline as the TIC functi-
on. The TIC function will then be executed first.
Example: James -Mgr
James -Mgr -M=MgrMsg
TIC - The Tic parameter activates the following functions:
first of all James will clean the outbound directory. James
will do this by checking all files in this directory against
the file-attached messages in your Netmail directory. Files
which are not attached to a message are considered to be send,
and thus will be deleted. The only not-attached file that
James will not delete is the Files.Bbs file.
Example: James -Tic
SCAN - When Scan is given as a parameter, James will scan your
netmail directory for messages addressed to JamesMgr, JamesFix
and FileFix. These messages are requests from your downlinks
for connecting and disconnecting magic files and/or tick
areas. The node sending the message can include some meta-
strings in his request message:
%L{IST} to list all available files/tick areas
%Q{UERY} to list all connected files/tick areas
%H{ELP} to request help about the JamesMgr
%+ALL to connect all available files/tick areas
%-ALL to disconnect all available files/tick areas
24
{+} LIST - With the list function you send a message to all the
connected nodes containing a list of all connected files/are-
as, and a list of all available files/areas.
Example: James -List
H - With the H parameter you can Hatch a file. Hatching of
files means that you enter a file into a file area. You should
know whether or not your uplink allows you to hatch files into
the area you want to hatch a file into. When the H parameter
is all you give, you are prompted for the information required
for the hatch process. You can also use the H parameter as
H=FileName. FileName is then as ascii file containing the
filename, area, description and origin address just as if it
was a tick control file.
Example: James -H
James -H=Dummy.Tic
FL= - When James finds the FL= parameter on the commandline,
James will scan the Hudson message for messages in the defined
local boards addressed to the persons defined in the userfile.
When James finds such a message James will export this message
to the Netmail directory, and sending it to the address speci-
fied in the datafile. The format of this parameter is:
-Fl=UserFile
The UserFile contains one user per line in the same way as the
users are defined with the T= parameter. You may specify the
M= parameter also. The message text defined in the file given
with the M= parameter will precede the original message text.
Example: James -Fl=Users.Dat
James -Fl=Users.Dat -M=FlHeader
ON= - With the ON= you can specify on which days the message
have to be send. You run James every day, but only on the days
given with the ON= parameter James will send messages.
Example: James -On=SunTueThu
Example: James -On=Mon
0=..9= - With these ten parameters you can specify a variable
on the commandline, and with the %Var0..%Var9 you can include
those parameter in your message text. The value of those
25
parameters have to be given between '"'.
Example: James -M=James -T=New,2:282/5 -N -0="c:\HIO.KEY"
CC - When you include the CC parameter with any other command-
line parameter, a Carbon Copy of new created messages will be
send to the person defined in the CC Addressee section of
JamesCfg.
Example James -Scan -CC
SR - The SR parameter (Skip Reset) can be used with message
which include a listing of new files and/or new tick files.
When you use this parameter, the time information will not be
updated. In this way you can send more than one announcement
in a very simple way. When you run James after you ran James
with the SR parameter, James does not know about the previous
send information.
Example: James -M=NewFiles -T=All_Sysops -E=1,2 -B=1 -SR
SM - The SM parameter (Skip Move) tells James not to move the
file you are hatching. This parameter can only be used with
the H parameter.
Example: James -H -SM
LOCAL - The LOCAL parameter allows you to test the Request
function. When you include the LOCAL parameter on the command-
line, James will also answer locally generated messages in the
searches. Use this parameter only for test purposes!
Example: James -R -B=13 -LOCAL
26
JAMES MESSAGE METASTRINGS
──────────────────────────────────────────────────────────────
James has the capability to replace information in your messa-
ge files by other information. When you include a 'metastring'
this string will be replace by the appropriate value. In this
way, for the reader of the message, it is possible to let a
message look just as if you entered it manually. Below is a
listing of all metastring divided into some logical groups.
Names
%BoardName Name of Bulletin Board as defined in James-
Cfg.
%Day Current day (1..31).
%FirstFrom First name of sender of message.
%FirstSys First name of sysop as defined in JamesCfg.
%FirstTo First name of addressee of message.
%FromName Name of sender of message.
%LastDay Day when James has done a check for new files
for the last time (1..31).
%LastFrom Last name of sender of message.
%LastMonth Month when James has done a check for new
files for the last time (1..12).
%LastStrMonth Month when James has done a check for new
files for the last time (jan..dec as defined
in JamesCfg).
%LastSys Last name of Sysop as defined in JamesCfg.
%LastTo Last name of addressee of message.
%LastYear Year when James has done a check for new fi-
les for the last time.
%LocalFolder Name of local folder when using FL= parameter
where the original message was found.
27
%Month Current month (1..12).
%Pw Password of node for manager messages. Is
only valid when Scan of Mgr parameter is
used.
%StrDay Current day (sun..sat as defined in James-
Cfg).
%StrMonth Current month (jan..dec as defined in James-
Cfg).
%SysName Names of Sysop as defined in JamesCfg.
%ToName Name of addressee of message.
%Var0..%Var9 The contents of the commandline parameters
0=..9=.
%Version Version of James.
%Year Current Year.
Addresses
Addresses are only valid for Netmail en Echomail messages.
Addresses of addressee are only valid for Netmail messages.
%FromAddress Origin address of message.
%FromNet Net number of origin address of message.
%FromNode Node number of origin address of message.
%FromPoint Point number of origin address of message.
%FromZone Zone number of origin address of message.
%ToAddress Destination address of message.
%ToNet Net number of destination address of message.
%ToNode Node number of destination address of messa-
ge.
%ToPoint Point number of destination address of messa-
28
ge.
%ToZone Zone number of destination address of messa-
ge.
Files
%Desc Description defined in JamesCfg of magic file
when MGR parameter is used.
%FileName File name in case of a file-attached message.
%MagicName Magic name of file attached file when MGR
parameter is used.
%NewFiles New files found in file-areas since last run
of James with %NewFiles metastring. When you
want to announce new files in a specific
group of areas, you can add :Groups to this
meta-string. Eg. %NewFiles:ACF to announce
only those new files found in areas belonging
to groups A, C and F. Do NOT forget to add
the /SR switch to the commandline when you
want to make other announcements (The marker
will otherwise be reset to the current time
and date, and James will not find any new
messages).
%NewTicks New arrived Tick files in Tick-areas since
last run of James with %NewTicks metastring.
When you want to announce new arrivced ticks
in a specific group of areas, you can add
:Goups to this meta-string. Eg. %NewTicks:GYD
to announce only those new ticks arrived in
the areas belonging to groups G, Y and D. Do
NOT forget to add te /SR switch to the com-
mand line when you want to announce those new
ticks in an other message.
%ReqFiles Files found matching searchmask when R para-
meter is used.
%ReqMask Searchmask given by user in original message
found when R parameter is used.
29
%UploadedFiles The filenames of the files a user has uploa-
ded when U parameter is used.
Sizes
%DriveSizeXN Size of drive X using N positions in message
in bytes. The size will be right justified.
%FileKb Size of attached file in case of a file-atta-
ched message in KiloBytes (1024 bytes).
%FileSize Size of attached file in case of a file-atta-
ched message in bytes.
%FreeXN Free space on drive X in N positions in mes-
sage in bytes. The size will be right justi-
fied.
%KbDriveSizeXN Size of drive X using N positions in message
in KiloBytes. The size will be right justi-
fied.
%KbFreeXN Free space on drive X in N positions in mes-
sage in KiloBytes. The size will be right
justified.
%KbNewFiles Total KiloBytes of new files found when %New-
Files is used in same message.
%KbUploadedFi- Total KiloBytes of files uploaded by user
les when U parameter is used.
%NrNewFiles Number of new files found when %NewFiles is
used in same message.
%NrReqFiles Number of files found matching the searchmask
found when using the R parameter.
%NrUploadedFi- Number of files uploaded by user when U para-
les meter is used.
%PFreeXN Percentage free on drive X in N positions in
message. The percentage will be right justi-
fied.
30
%SizeNewFiles Total bytes of new files found when %NewFiles
is used in same message.
%SizeUploaded- Total size of files uploaded by user when U
Files parameter is used.
Statistics
%CarbonCopiesT- Number of Carbon Copy messages send in the
hisWeek past seven days, or since last reset.
%CarbonCopie- Number of Carbon Copy message send today.
sToday
%ExportedThis- Number of netmail messages exported in the
Week past seven days or since last reset.
%ExportedToday Number of netmail messages exported today.
%ForwardedThis- Number of messages forwarded from local
Week boards in the past seven days or since last
reset.
%ForwardedToday Number of messages forwarded from local
boards today.
%ImportedThis- Number of netmail messages imported in the
Week past seven days, or since last reset.
%ImportedToday Number of netmail message imported today.
%NewSizeKBThis- Total size in KiloBytes of new files found in
Week the past seven days or since last reset.
%NewSizeKbToday Total size in KiloBytes of new files found
today.
%NewSizeThis- Total size in bytes of new files found in the
Week past seven days or since last reset.
%NewSizeToday Total size in bytes of new files found today.
%NrFilesThis- Number of new files found in the past seven
Week days or since last reset.
31
%NrFilesToday Number of new files found today.
%RequestsThis- Number of searchrequests answered in the past
Week seven days or since last reset.
%RequestsToday Number of searchrequests answered today.
%ThankYouThis- Number of user thanked for uploads in the
Week past seven days or since last reset.
%ThankYouToday Number of users thanked for uploads today.
%TotalThisWeek Total number of messages send in the past
seven days, or since last reset.
%TotalToday Total number of messages send today.
%WelcomeThis- Number of new users welcomed in the past se-
Week ven days or since last reset.
%WelcomeToday Number of new users welcomed today.
32
FILE NAMING CONVENTION
──────────────────────────────────────────────────────────────
James creates several files by itself which have a hardcoded
name. These files will be created in the James directory.
James.Cfg Default configuration file
James.His History file about the amount of messages
send etc.
James.Nde This file contains the information about your
uplink and downlink nodes.
James.Fls This file contains the information about your
magic files.
James.Are This is the file which contains the definiti-
ons of your Tick areas.
James.Dup File containing the CRC32 checks used for
duplicate checking.
James.Tci File containing the information about new
receive tick files.
James.Key Keyfile you will receive when you register
James.
33
EXAMPLE MESSAGE FILES
──────────────────────────────────────────────────────────────
Included in this package is a file called Examples.Zip. This
file contains some example messages to help you on the way,
and to show you what can be done with James.
DailyRep.Msg This message includes some statistical infor-
mation about your BBS, and the thing james
has been doing.
Usage: James -M=Dailyrep -T=Sysop -B=10
FlHeader.Msg With these two files you can forward messages
Flocal.Dat from your defined local boards to the users
defined in the Flocal.dat file.
Usage: James -Fl=Flocal.Dat -M=FlHeader
Manager.Msg This message can be use as a message accompa-
nying files which you forward to your down-
links.
Usage: James -Mgr -M=Manager
NewFiles.Msg With this message you can announce new files
which are moved to your BBS file-areas in a
message.
Usage: James -M=NewFiles -T=All -B=35 -E
NewUser.Msg This is an example of a message which you can
send to a new user on your system.
Usage: James -W -M=NewUser -B=10
UplFiles.Msg When you use this message with the -U parame-
ter, James will send the message to all uplo-
aders.
Usage: James -U -M=UplFiles -B=10
34
